February 5th, 2003, 05:35 PM
Help! Host is assumed to be a nameserver
I'm no DNS expert, so I'm not even sure if the title is correct, but let me give you some background:
I had a domain registered with NetworkSolutions. Due to some DNS misconfigurations, my www.domain.com was assumed to be a host/nameserver.
I left NetworkSolutions because, well they suck (topic for another forum), and hoped this problem would go away. But I recently changed my dns and all my records are resolving fine except my www record. DIG resolves it as an A record, but its really a CNAME. It seems like the root servers still assume its a nameserver and are gluing its last known IP.
I'm pretty sure my dns entries are correct because I'm using a dns provider's interface to manage my zone.
Anyone know what's going on?
February 7th, 2003, 02:53 PM
just because you are using your providerīs interface does not say it will setup it correctly. too many providers have no clue about what they are doing
using "A records" instead of "CNAME"s is "best practise" though. this is no mistake in the setup.
sorry, i canīt remember straight from my head why, but if you are really curious, read some security books or online sites.
i just found another interesting thread for you about CNAME vs. A Record: http://forums.devshed.com/t51482/s.html
Last edited by M.Hirsch; February 7th, 2003 at 02:59 PM.
February 7th, 2003, 03:00 PM
Actually, I recently found out what the problem is. Even though I left Network Solutions, they still have the host as a name server.
Bottom line is this really screws up my dns. So I have to have NS remove that host as a name server.