We were having a small problem here and I traced it down to a reverse DNS lookup on a 172.16 address hanging. I noticed that a.root-servers.net reports that BLACKHOLE.ISI.EDU is authoritative for 16.172.in-addr.arpa. Is this the way it should be, or is the yet another network solutions mistake? Who should really handle DNS for rfc1918 addresses? Grisha
We were having a small problem here and I traced it down to a reverse DNS lookup on a 172.16 address hanging.
I noticed that a.root-servers.net reports that BLACKHOLE.ISI.EDU is authoritative for 16.172.in-addr.arpa.
Is this the way it should be, or is the yet another network solutions mistake? Who should really handle DNS for rfc1918 addresses?
Grisha
This is accurate. --bill
We were having a small problem here and I traced it down to a reverse DNS lookup on a 172.16 address hanging.
hmm...yeah. they'll do that.
I noticed that a.root-servers.net reports that BLACKHOLE.ISI.EDU is authoritative for 16.172.in-addr.arpa.
Is this the way it should be, or is the yet another network solutions mistake? Who should really handle DNS for rfc1918 addresses?
well...imho, they should be delegated to localhost. and everyone should have a localhost zone with the proper address in it, to go with their 127.in-addr.arpa zone file. but then again, some people think i'm weird. -- |-----< "CODE WARRIOR" >-----| codewarrior@daemon.org * "ah! i see you have the internet twofsonet@graffiti.com (Andrew Brown) that goes *ping*!" andrew@crossbar.com * "information is power -- share the wealth."
well...imho, they should be delegated to localhost. and everyone should have a localhost zone with the proper address in it, to go with their 127.in-addr.arpa zone file.
but then again, some people think i'm weird.
--
Well, in that context all of RFC 1918 space should never have been delegated and private networks built out of 127.0.0.0/8. In the mists of time, I actually built a network that way. Seems that the prevaling wisdom was to delegate whole other blocks for tom-foolery. Given the lax registration checking, it was considered prudent to actually have real servers host these zones so the possiblity of "hijacking" would be reduced. There was a recent attempt to actually have the servers provide an authoritative response when a query was received. This engendered a significant raft of unexpected responses. Apparently several fortune 1000 companies have used this space for network mgmt. and propogate the prefixes in the Internet. This will be much to their dismay when authoritative replies are once more available. YMMV.
participants (3)
-
Andrew Brown -
bmanning＠vacation.karoshi.com -
grisha＠verio.net