Tag Info

New answers tagged

-1

 Your current DNS pointing to old server DNS as mentioned in comment(ns59.1&1.co.uk , ns60.1&1.co.uk ).You should ask the hosting provider of new server about the DNS records and edit the DNS record entry according to that. Mostly its as ns1.my domain.com and ns2.my domain.com. They will fix it for you. This needs to be done from both ends(domain ...


2

It's not uncommon for the name servers to exist somewhere other than the Registrar. Many web hosting companies tell customers to move their name servers to the web hosting company (some may even require it although there's no technical requirement for a web host to also host the DNS). Many "individual" web hosters also tell their customers to move their name ...


0

Confirm from your client about the configuration if you don't have the access to do them by yourself. IP address is required for A record entry and dns is also required for domain name resolving. Both of them should be pointing correctly.And also its depend upon TTL time (how much time it will take to propagate). Currently dig command shows this if its ...


5

The problem is that websitewelcome.com effectively delegated the domain to 1and1: $ dig NS uptowngreenville.com @ns1144.websitewelcome.com ... ;; ANSWER SECTION: uptowngreenville.com. 86400 IN NS ns58.1and1.com. uptowngreenville.com. 86400 IN NS ns57.1and1.com. Also weird, when you trace the resolution, the upstream resolver gives ...



Top 50 recent answers are included