Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  


Welcome to Hurricane Electric's forums!

Pages: 1 2 [3] 4 5 ... 10
 on: December 16, 2018, 07:29:40 AM 
Started by IsaacFL - Last post by kriteknetworks
As opposed to running your own nat64 setup, with 100% control over it, and not having to make your traffic traverse networks it doesn't need to, thus reducing overhead?

 on: December 15, 2018, 12:34:16 AM 
Started by deadclown - Last post by snarked
Technically, you do need NS records in the parent zone for the child zone, but when both zones are hosted on the same name servers, DNS programs generally shortcut the lookup through the parent and directly serve the child.  If the parent and child zones are on different servers, the NS records for the child are required in the parent zone for the former to be found.

In my zones, I do delegate even when both zones are on the same servers, and it works without error -- as it should.  NS records are meant to be in both the zones they define and that zone's parent.

 on: December 13, 2018, 09:20:49 PM 
Started by frgomes - Last post by polishpaul
Has anyone asked support about this?

 on: December 13, 2018, 02:09:56 PM 
Started by deadclown - Last post by polishpaul

In short:
1. Just add the subdomains in the apex zone.
2. Make sure you do NOT have NS records for your subdomain in the apex zone.

Support said:
"In general, there's no need to create a zone for a subdomain.  The zone for the apex domain can contain records for subdomains, sub-subdomains, etc."
But then
"Actually, I have to correct myself: while you can use the method I described to add a subdomain's zone, this results in undefined behavior.  RFC dictates that nameservers not delegate subdomains to themselves.  Sometimes it works, sometimes it doesn't.  Right now you're getting "BAD (HORIZONTAL) REFERRAL" results, which is a common consequence."

So I wondered, why are my subdomains not resolving? Its because i had the subdomain NS records setup in the apex zone!!! Once I removed my NS records (for, or the subdomain i wanted to add) my records started to resolve!

 on: December 13, 2018, 12:49:28 PM 
Started by deadclown - Last post by polishpaul
I'm having problems setting this up too. I kept adding a subdomain but i keep getting an error

Zone failed validation test. ERROR: Delegation was not found. Please delegate to ns1, ns2, ns3, ns4 and then retry. ( /

Eventually this worked! I'm not sure what helped but i was still in the process of moving the main domain from my old host, so i pointed the delegation back to the "old" dns servers, which had an SOA record for this sub-domain. Perhaps that's what allowed the creation? Not sure...

I must have tried adding this a few dozen times while experimenting and eventually it worked and now I have an SOA in and this subdomain works fine.

However, i cannot get this to work for any other domains (they never had any subdomains). I have NS records created in the main domain, for example, but i still cannot create any subdomains...

So what is the proper way to do this? Is this documented anywhere in a wiki?

 on: December 13, 2018, 10:43:31 AM 
Started by CootesNest - Last post by CootesNest
I don't know if this is my setup, but, between 18:13 and 19:13 on the above date, my cron job to refresh the ip address stopped working with the following error:
curl: (51) SSL: no alternative certificate subject name matches target host name ''

I think that the issue may be a missing (at least as far as cron 7.55.1 is concerned) Subject Alt Name in the certificate.

One oddity: the command succeeds with `-6`, but not with `-4`:
`curl -4  "https://<my loging>:<pwd><fqdn>"`

 on: December 12, 2018, 02:18:27 AM 
Started by deadclown - Last post by Paxy
did you delegate your domain to be managed by HE's NS servers? You can't just delegate only a subdomain...
Why can't you delegate just some sub-domain to HE DNS? It worked one month ago!

 on: December 11, 2018, 03:59:34 AM 
Started by bugalaza - Last post by bugalaza
Solved. Problem detected on a specific server.

 on: December 10, 2018, 07:06:49 PM 
Started by bugalaza - Last post by broquea
Only IRC & SMTP are filtered until Sage access when the filters can be removed.

 on: December 10, 2018, 06:50:29 PM 
Started by bugalaza - Last post by bugalaza
Actually, now that I saw what I posted in the wrong forum. Please move to the forum Specific Topics. In fact it has nothing to do with DNS.
Regarding the need, as initially reported, port 445 is used to establish trust relationship in Active Directory, as well as authentication of users and computers.

Pages: 1 2 [3] 4 5 ... 10