Moved my server to a new server (new ip) but dig @localhost still shows old ip

Discussion in 'Server Operation' started by brisk, Feb 23, 2019.

  1. brisk

    brisk Member

    So I moved my server to a different machine, with a different ip. I changed ISPConfig server config to have a the new ip, and everything in ispconfig shows new ip, but dig @localhost on the new server still shows old ip... did I miss anything?

    On my namecheap account, the ns.mycompany.com was also changed to the new ip.

    Thanks
     
  2. brisk

    brisk Member

    Also is this correct?

    On the new server:
    Code:
    root@server1:~# dig @localhost www.mycom.com
    
    ; <<>> DiG 9.10.3-P4-Debian <<>> @localhost www.mycom.com
    ; (2 servers found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 36102
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;www.mycom.com.        IN    A
    
    ;; Query time: 0 msec
    ;; SERVER: ::1#53(::1)
    ;; WHEN: Fri Feb 22 23:12:15 EST 2019
    ;; MSG SIZE  rcvd: 46
    
    root@server1:~#
    
    
    But on my older server, was working:
    Code:
    root@server1:~# dig @localhost www.mycom.com
    
    ; <<>> DiG 9.10.3-P4-Debian <<>> @localhost www.mycom.com
    ; (2 servers found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18296
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;www.mycom.com.        IN    A
    
    ;; ANSWER SECTION:
    www.mycom.com.    3600    IN    A    199.95.31.87
    
    ;; AUTHORITY SECTION:
    mycom.com.        3600    IN    NS    ns6.dns.com.
    mycom.com.        3600    IN    NS    ns5.dns.com.
    
    ;; ADDITIONAL SECTION:
    ns5.dns.com.    3600    IN    A    199.95.31.87
    ns6.dns.com.    3600    IN    A    199.95.31.87
    
    ;; Query time: 0 msec
    ;; SERVER: ::1#53(::1)
    ;; WHEN: Fri Feb 22 23:15:28 EST 2019
    ;; MSG SIZE  rcvd: 139
    
    You have new mail in /var/mail/root
    root@server1:~#
    
     
  3. brisk

    brisk Member

    On the DNS server, if I do a "dig +trace www.mycom.com" I got this:

    Code:
    ;; BAD REFERRAL
    ;; Received 1188 bytes from 199.99.32.215#53(ns5.dns.com) in 0 ms
    
    But on the old working server I got this:

    Code:
    www.mycom.com.    3600    IN    A    192.98.31.87
    mycom.com.        3600    IN    NS    ns5.dns.com.
    mycom.com.        3600    IN    NS    ns6.dns.com.
    ;; Received 139 bytes from 192.98.31.87#53(ns5.dns.com) in 0 ms
    
     
  4. brisk

    brisk Member

    Problem solved!

    When I move the serve to a different server, even i backedup the /etc/bind folder and restored on the new server, but the zone files are still missing! The fix is to go to each zone settings in ispconfig, select any A record, click save (without changing anything, just save) then these zone file will be created, then it started working!
     
  5. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    You could have done resync services for DNS records in ISPConfig tab Tools, Sync Tools, Resync. This is not normally necessary, your setup must have been confused somehow.
     
  6. brisk

    brisk Member

    Thank you so much!
     

Share This Page