The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Migrated domains not resolving on source server

Discussion in 'General Discussion' started by DaveT, Nov 20, 2005.

  1. DaveT

    DaveT Active Member

    Joined:
    Aug 20, 2004
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    1
    Hi,

    I've hit an interesting problem.

    I migrated domaina and domainb from servera to serverb using WHM's "Copy an account from another server" feature which went smootly.

    I then switched my dns over which again went smoothly.

    I then deleted the accounts for domaina and domainb from the source server (servera).

    On servera now however, I can't resolve either domaina or domainb using the local named instance. The only way I could get the domains to resolve was to add a non-local name server into /etc/resolv.conf

    This is causing issues with mail since one of the accounts migrated to serverb needs to send mail to accounts on servera but they get bounced since the rdns lookup that exim performs is failing.

    Has anyone else come across this, or have any possible suggestions? named on servera is resolving other external sites (such as microsoft.com cpanel.net etc) successfully, it's just refusing to resolve these two migrated domains.

    /etc/named.conf hasn't any entries for domaina or domainb
    /etc/localdomains hasn't any entires for domaina or domainb

    Any thoughts appreciated...

    Dave.
     
  2. anand

    anand Well-Known Member

    Joined:
    Nov 11, 2002
    Messages:
    1,435
    Likes Received:
    1
    Trophy Points:
    38
    Location:
    India
    cPanel Access Level:
    DataCenter Provider
    On the console what is the output of the following

    Code:
    dig domaina.com
    and

    Code:
    dig domainb.com
    Also what are the contents of your /etc/resolv.conf ?
     
  3. DaveT

    DaveT Active Member

    Joined:
    Aug 20, 2004
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    1
    Hi Anand,

    /etc/resolve.conf has

    nameserver 207.58.135.50

    in it (this is the ip address of the server)

    In both cases, a dig indicates a servfail condition... here's one of them

    ; <<>> DiG 9.2.1 <<>> firstforhosts.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 36436
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;firstforhosts.com. IN A

    ;; Query time: 20 msec
    ;; SERVER: 207.58.135.50#53(207.58.135.50)
    ;; WHEN: Mon Nov 21 14:13:10 2005
    ;; MSG SIZE rcvd: 35

    A dig against any other domain (other than the migrated ones) works fine - here's microsoft.com for example

    ; <<>> DiG 9.2.1 <<>> microsoft.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26467
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 5, ADDITIONAL: 5

    ;; QUESTION SECTION:
    ;microsoft.com. IN A

    ;; ANSWER SECTION:
    microsoft.com. 3600 IN A 207.46.130.108
    microsoft.com. 3600 IN A 207.46.250.119

    ;; AUTHORITY SECTION:
    microsoft.com. 172800 IN NS ns3.msft.net.
    microsoft.com. 172800 IN NS ns4.msft.net.
    microsoft.com. 172800 IN NS ns5.msft.net.
    microsoft.com. 172800 IN NS ns1.msft.net.
    microsoft.com. 172800 IN NS ns2.msft.net.

    ;; ADDITIONAL SECTION:
    ns1.msft.net. 172800 IN A 207.46.245.230
    ns2.msft.net. 172800 IN A 64.4.25.30
    ns3.msft.net. 172800 IN A 213.199.144.151
    ns4.msft.net. 172800 IN A 207.46.66.75
    ns5.msft.net. 172800 IN A 207.46.138.20

    ;; Query time: 179 msec
    ;; SERVER: 207.58.135.50#53(207.58.135.50)
    ;; WHEN: Mon Nov 21 14:14:46 2005
    ;; MSG SIZE rcvd: 241

    Any thoughts you might have would be appreciated...

    Dave.
     
Loading...

Share This Page