Verisign DNS change broke my HP printer!
 

"I have an HP Deskjet 6127 which has a built-in NIC and TCP/IP printing capability. Just a basic printer used by one small department and it's been working fine since it was setup. I have a simple LAN with one main W2K Server running DHCP and DNS. I usually setup any shared printer on this server, so installed the HP software which sets up a TCP/IP local port and points it at the printer. As the printer was setup to use DHCP for ease of use the TCP/IP printer port maps via the printer's name.

Today, for no apparent reason, print jobs just stuck in the queue for a few minutes before timing out. To make a long and tedious set of troubleshooting steps short, it turned out the problem was the Verisign DNS change. Due to the way DNS is setup on the server (Because it is the LAN's top-level DNS server) a search for the local printer was being routed via the Internet. I guess it must always have worked this way, but because the printer would never resolve to a routable IP address it must have then tried a local lookup.

Anyhow now, thanks to Verisign, my server always resolves the printer to the external IP address for their search service, hence the dead print jobs, forcing me to move the printer share to a different server. "


http://www.theregister.co.uk/content/6/32872.html





:helpme :helpme :helpme

http://www.isc.org/products/BIND/delegation-only.html

Do the right thing patch your nameservers or annoy the fuck out of your uplink to patch their nameservers.

Fuck verisign.

hmm looks like its all ready been deployed on certain providers

:ak47: