Registrar based on FQDN or IP ?

Discussion in 'Installation/Configuration' started by kmchen, Jan 20, 2019.

  1. kmchen

    kmchen Member

    Hi, on a fresh debian server reinstall from wheezy to stretch/ispconfig3.1, I have 2 domains using mail with postfix/Dovecot. One works fine, the other worked briefly at start and do not at all after 24h.
    That server was installed on another IP failover 188.165.47.210 and has been reinstalled under its real IP 94.23.227.123
    The domain that do not work was hosted on that same server that did change of IP and had DNS definitions on the old IP before reinstallation. Now I see that the unworing domain is still reported by dig with the old IP:

    kmc@kmcs:~$ dig mail.unworking.fr

    ; <<>> DiG 9.10.3-P4-Debian <<>> mail.unworking.fr
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48391
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;mail.unworking.fr. IN A

    ;; ANSWER SECTION:
    mail.unworking.fr. 11426 IN A 188.165.47.210

    ;; Query time: 8 msec
    ;; SERVER: 8.8.8.8#53(8.8.8.8)
    ;; WHEN: Sat Jan 19 22:12:49 CET 2019
    ;; MSG SIZE rcvd: 60

    kmc@kmcs:~$ dig mail.working.com

    ; <<>> DiG 9.10.3-P4-Debian <<>> mail.working.com
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25006
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;mail.working.com. IN A

    ;; ANSWER SECTION:
    mail.working.com. 2996 IN A 94.23.227.123
    How can I force the unworking domain to use the new IP used to define both domains on the hosting server ?
    Domain definition at registrar are based on FQDN or IP ?
    I noticed that the problem appears at MAIL level. WEB work fine.
     
    Last edited: Jan 20, 2019
    kmchen, Jan 20, 2019
    #1
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    FQDN.
    If name service returns wrong IP for you hostname, you have to enter the correct IP in name service and wait for 4 to 48 hours until the new info shows everywhere.
    If you do not know what are the name servers for your domain, try
    Code:
    whois unworking.com | egrep -i "(name|server)"
    It would be better to test name service info with command host instead of dig. https://www.howtoforge.com/tutorial/setting-up-your-own-name-service-with-ispconfig/#nbsptesting
     
    Taleman, Jan 20, 2019
    #2
  3. kmchen

    kmchen Member

    It appears that it was a DNS propagation delay (and a dovecot conf problem).
    Now all my emails accounts work fine
     
    kmchen, Jan 20, 2019
    #3

Share This Page