Luc MAIGNAN wrote: > Hi list, > > I've a DNS behaviour I don't understand. > > > 1/ I've a DNS server which resolves mydomain.com and some aliases : > server.mydomain.com (the alias is put in the zone file like this : > SERVER A the_ip) > 2/ from the DNS server,all is right : dig mydomain.com and dig > server.domain.com give the good informations > 3/ from a computer somewhere on the internet, a dig mydomain.com give > the Ip address of the server, but server.mydomain.com can't be resolved. > > The only way to have resolutions is to give the ip address of my server > as the primary dns of the internet connexion, but unfortenaly, I can't > ask all people of the world to do this..... > > Can somebody help me ? > > Very best regards > The problem is not on your local machine. It is with the primary name server for your domain. Without real information that is about as much as we can tell you. You need to update the DNS record to add a record for server.mydomain.com. What type of record depends on what you are trying to do. How you do it depends on who is providing the name servers. From what little you have told us, it sounds like you are getting the name servers as part of your domain name registration. There is probably a web form to modify the records. One thing to keep in mind - when you change the DNS records, it takes a while for the changes to show up everywhere. A lot of ISPs are running caching name servers, and if the entries for your domain are in the cache, then they have to expire before the server checks again. This can include an entry for server.mydomain.com that basically says that the name server for the mydomain.com says that server.mydomain.com does not exist. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
