I have a networking question:
When I was on DSL I ran my own DNS server. I had several hosts behind NAT, so they had 10.1.1.x addresses and that's what their entries in DNS said. The wierd part is that if a query was made from outside NAT the answer would come back as the address of the router (Cisco 675). So instead of getting 10.1.1.12 I'd get 199.104.125.150. This was great for my purposes 'cause I'd forward ssh to one machine and http to another and I could address them by name and still get to the right place.
So what I'm wondering is why? Who made it work that way? Is BIND smart enough to give different answers to different queries? Did the Cisco 675 take the UDP response packet and translate the address? Is that part of NAT?
Zone transfers (which use TCP) didn't get the translated names, only regular UDP queries.
Well, that is pretty wierd.
BIND can be that smart if you tell it to be with the "views" directive (I am guessing by your post that you didn't).
Well, I tested what I think you are describing and it looks like the Cisco 675 is changing the addresses. Unfortunately, it is changing the addresses for all queries, including those addresses that are /outside/ the NAT range. I have entries like the following in my zone file:
banana A 10.0.0.128 sarah A 208.187.xx.xx
And running some commands from the outside we get:
[EMAIL PROTECTED] adama]$ dig @c675 banana.example.com +short 65.100.xx.xx [EMAIL PROTECTED] adama]$ dig @c675 sarah.example.com +short 65.100.xx.xx
65.100.xx.xx is the address of c675 the Cisco 675 router. Running ethereal on the DNS server shows correct response regardless of destination.
I will ask some Cisco people. I'll post if I find anything out.
Adam Augustine
____________________
BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
