New .de Domain wont register successfull

prostream · 2019-01-30 15:07:16 UTC

Hi,

i´m currently running my MIAB with about 7 .de Domains. They´re hosted at 1und1 and i only edited the nameservers in the 1und1 control panel to my box nameservers.

Now i want to add a new .de Domain and edited the nameservers at the 1und1 control panel. Some seconds after changing it 1und1 throws an error that this procedure has not succeed. While looking into my syslog it shows me a lot of these entries:

    Jan 30 07:23:52 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 79.137.84.65#53
Jan 30 07:23:52 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 109.201.133.61#53
Jan 30 07:23:52 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 108.59.2.202#53
Jan 30 07:23:52 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 46.165.221.164#53
Jan 30 07:23:52 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 79.137.84.65#53
Jan 30 07:23:52 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 109.201.133.61#53
Jan 30 07:23:52 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 108.59.2.202#53
Jan 30 07:23:54 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 46.165.221.164#53
Jan 30 07:23:54 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 79.137.84.65#53
Jan 30 07:23:54 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 109.201.133.61#53
Jan 30 07:23:55 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 108.59.2.202#53
Jan 30 07:23:55 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 46.165.221.164#53
Jan 30 07:23:55 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 79.137.84.65#53
Jan 30 07:23:55 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 109.201.133.61#53
Jan 30 07:23:55 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 108.59.2.202#53
Jan 30 07:23:57 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 46.165.221.164#53
Jan 30 07:23:57 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 79.137.84.65#53
Jan 30 07:23:57 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 109.201.133.61#53
Jan 30 07:23:57 box named[1068]: error (unexpected RCODE REFUSED) resolving 'mailing.loan/A/IN': 108.59.2.202#53

Checking the affected Domain at https://www.denic.de/service/tools/nast/ shows:

I cannot even imagine if this is an error from Denic or from my DNS settings.
Can anyone help?

alento · 2019-01-30 22:49:25 UTC

Is MiaB controlling the DNS service for your domains, or is it controlled externally?

I suspect that you need to add the DNS entries (either by adding the domain with a new user at MiaB or at your external DNS service provider - whichever is applicable) FIRST before changing the name servers at 1und1.

The error you are seeing says that MiaB is not set up to provide DNS to that domain and is unable to get a response from a request forwarded to another server. In other words, the entries are non existent.

prostream · 2019-01-31 07:40:29 UTC

Thanks for your reply!

Yes MIAB is controlling my DNS service for my domains.

That’s exactly what I did! First made the domain MIAB known (by creating a new email address with the domain) and then changed the nameservers at 1und1. Unfortunately I still get the same error.

Never had any kind of problems with other .de domains…

Status check shows that nameservers are set correctly:

prostream · 2019-01-31 07:50:16 UTC

Changing another .de domain from the exact same 1und1 account works without problems. The domain was registered 48h ago… Could that have something to do with this?

alento · 2019-01-31 07:50:40 UTC

I think that this IS a problem with .de specifically. .de domains require name servers on two separate IP’s. If you have time available we could do a quick test … but I think that you are going to have to set up and enable Secondary DNS.

prostream · 2019-01-31 07:51:58 UTC

yes we can do a quick test if you would like. Ok that’s crazy, because the other .de domains all work.

alento · 2019-01-31 10:13:39 UTC

UPDATE:

Supposedly .de domains require two name servers using different IP addresses. This is not the issue here as OP has other .de domains working just fine on this instance of MiaB.
We tested using secondary DNS anyways, but still no luck.

I noticed using dig on the OP’s MiaB ns1 name server that the records are NOT being served for this domain, but they ARE for other domains.

All 3 zone files are present in /etc/nsd/zones for this domain.

Maybe someone has some other ideas … @murgero

murgero · 2019-01-31 15:48:14 UTC

Nameserver records need to be made first before anything else. Login to registrar and setup nameserver records. Even if two are the same IP doesn’t matter.

prostream · 2019-01-31 16:20:29 UTC

So I got that right. First enter the name server at the serviceprovider (in my case 1und1) and then make the domain known to MIAB by creating a mail user?

Edit: First entering the nameservers and then making it known to MIAB didn’t help…

murgero · 2019-01-31 16:25:25 UTC

This will take anywhere from 1 hour to 48 hours to be configured. Once the nameservers are set you will need to wait AT MAX 2 days.

Once you get back the proper IP/hostname when checking the NS records then add to MIAB

Windows:
nslookup -type=NS domain.de

Linux:
dig domain.de NS

prostream · 2019-01-31 16:26:11 UTC

This is very confusing… Never had to wait more than 30 Minutes to update .de Domains… But i will try!

And 1und1 is telling me that there is something wrong. This error won´t go away from itself - the 1und1 support told me…

murgero · 2019-01-31 16:28:11 UTC

The nameserver for the domain pictured must have just updated as I can see it on my end now.

I’m sorry, your english is a little weird to read, to confirm, the error displayed cannot be resolved by 1und1?

prostream · 2019-01-31 16:30:07 UTC

Sorry for that… No they told me it has something to do with the DENIC.

murgero · 2019-01-31 16:31:42 UTC

Well the name server seems to point to your MIAB install (ns1.box.domain.de) so I would give it a shot now.,

prostream · 2019-01-31 16:38:48 UTC

So just wait? But the error message at 1und1 control center is still confusing me…

murgero · 2019-01-31 22:03:26 UTC

Did you make DNS entries under the “Custom DNS” page??

prostream · 2019-01-31 22:14:13 UTC

no i didn’t put anything in there

alento · 2019-02-01 00:11:07 UTC

@murgero
Here is what is troubling me … I use gwhois.com to confirm WHOIS, name servers, and DNS records. ALWAYS when the name servers are updated at the registrar that is shown instantly, or within a few minutes in the WHOIS lookup. If you look at the domain now, the registrars name servers are showing. Now the completely odd thing is that yes, they are announcing the MiaB name servers as authoritative name servers for the domain, but are NOT sending the requests to the MiaB.

DENIC states that all ,de domains must have name servers on two separate IP addresses. This is clearly not the case as the OP has other .de domains successfully being handled on this same MiaB.

The error that the OP keeps getting seems to be a rejection by DENIC of the name servers for this domain, but yet other .de domains are working just fine.

I am rather convinced that this is a 1and1 and DENIC issue …

But, let’s wait the 48 hours and see what happens. What other choice do we have?

prostream · 2019-02-01 07:53:37 UTC

I have contacted 1und1 again about this. The case is now in second level support. Let’s see if they can solve it.

alento · 2019-02-04 02:17:15 UTC

Just checking to see if any updates. I do not see any changes on the domain with the tools I check with.