To make managing a few things simpler on CTWUG I had to remove the ability to create IP address entries that point a specific host to multiple IP addresses.
I assume this would usually be done to have rb.mynode.ctwug.za.net point to all the ip addresses of the rb. This causes problems as people don’t keep these up to date. IPs get moved etc and now rb.mynode points two to seperate devices. Now we start to monitor these devices or check their configurations and it ends up in a mess.
Where rb had ip address entry 172.18.10.1 and 172.18.10.2 I’ve renamed them to rb-172-18-10-1 and rb-172-18-10-2 respectively.
It should still be possible to set things up in similar fashion but here you’d end up with something less problematic to manage centrally. But this still looks the same when you do nslookup.
- Set “rb” and “172.18.10.1” for forward and reverse IP address. This would probably be the OSPF router ID.
- Under forward add "rb-link-A and “172.18.10.2”.
- You could also add “rb-link-B” and “172.18.10.1” under forward
- Under reverse add “rb” and “172.18.10.2”.
With the above setup you will have
nslookup rb.mynode.ctwug.za.net gives 172.18.10.1
nslookup rb-link-A.mynode.ctwug.za.net gives 172.18.10.2
nslookup rb-link-B.mynode.ctwug.za.net gives 172.18.10.1
nslookup 172.18.10.1 gives rb.mynode.ctwug.za.net
nslookup 172.18.10.2 gives rb.mynode.ctwug.za.net
I.e. forward lookups are possible in multiple ways. Reverse lookups always give the same answer. Therefore in traces your rb will always pop up under it’s main name. Would be handy if this main name also is the OSPF router ID 