# Destination IP rewrite NHLD

**URL:** <https://community.a10networks.com/t/destination-ip-rewrite-nhld/824>\
**Category:** ADC - Application Delivery\
**Tags:** nhld, slb-adc\
**Created:** [February 1, 2024, 8:26pm UTC](https://community.a10networks.com/t/destination-ip-rewrite-nhld/824 "2024-02-01T20:26:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anfovar](https://avatars.discourse-cdn.com/v4/letter/a/bc79bd/32.png) [@anfovar](https://community.a10networks.com/u/anfovar)\
**Post date:** [February 1, 2024, 8:26pm UTC](https://community.a10networks.com/t/destination-ip-rewrite-nhld/824/1 "2024-02-01T20:26:10Z")

</div>

Hi Guys

Is there a way to rewrite a Destination IP based in NHLD?

For example if an internal client send traffic to the IP 1.1.1.1 the Wildcard will receive the traffic and the A10 will rewrite the destination from 1.1.1.1 to 20.20.20.20

---

<div class="post-metadata">

**Author:** ![mdunn](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mdunn](https://community.a10networks.com/u/mdunn)\
**Post date:** [February 5, 2024, 7:14pm UTC](https://community.a10networks.com/t/destination-ip-rewrite-nhld/824/2 "2024-02-05T19:14:56Z")

</div>

With NHLD, we are typically load balancing traffic destined for the public internet across multiple firewalls or routers. To support this traffic flow, we configure wildcard vips with “no-dest-nat” on the virtual services. That in mind, what is the use-case here to deviate from this functionality?  
For flows such as these, it may be simpler to configure a VIP with an IP address of the destination to intercept (1.1.1.1) and configure a service-group with slb server member of 20.20.20.20.