On 11 July 2017 at 14:30, Oliver Stirling <[email protected]> wrote: > Hi, > > I wonder if there is someone that can help, for our BT customers (and > possibly TalkTalk) any DNS lookup for hosting.cloudnext.net is returning a > different IP (92.242.132.15) instead of the correct IP (79.170.44.8)
I have had a poke of the hosting.cloudnext.net domain from a few different locations, and it seems that the nameservers reply quickly most of the time, but very occasionally just don't respond at all before the timeout hits. I also note that the domain is non-delegating and isn't split into its own zone. There are no SOA records. If your nameservers are heavily loaded and therefore not responding in every instance, you might want to start breaking out into separate zones, especially if you have a lot of subdomains that share the same parent nameservers. Creating separate zones reduces the load on your parent nameservers. You also only have two nameservers even though RFC2182 recommends a minimum of three (with RFC1912 recommending a maximum of 7). To create separate zones you must assign this subdomain it's own nameservers responsible for this domain and remove these records from your parent zone. An SOA record must also be published that refers queries to the newly created primary nameserver. Worth a shot? Alex
