Hello,
I can not send mail to domain birac.ba
The domain birac.ba can not be resolved using Cloudflare DNS.
nslookup birac.ba 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1
*** No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available
for birac.ba
If I user Google it works fine:
nslookup birac.ba 8.8.8.8
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: birac.ba
Address: 81.93.78.35
Please advise.
If you have control over this domain, see below. If you don’t, you could try to reach out to them with the same information, but it’s nothing you can fix on your end.
It looks like one of the nameservers for birac.ba, sava.utic.net.ba on 195.130.35.3, is set at the registrar to be a nameserver but is referring back to itself, causing a bad delegation (horizontal referral).
dig birac.ba @ns.ba (Querying tld nameservers)
;; AUTHORITY SECTION:
birac.ba. 86400 IN NS linhost04.utic.net.ba.
birac.ba. 86400 IN NS sava.utic.net.ba.
;; ADDITIONAL SECTION:
sava.utic.net.ba. 8640 IN A 195.130.35.3
linhost04.utic.net.ba. 66475 IN A 195.130.35.146
dig birac.ba @195.130.35.3 (Sava)
;; QUESTION SECTION:
;birac.ba. IN A
;; AUTHORITY SECTION:
birac.ba. 86400 IN NS linhost04.utic.net.ba.
birac.ba. 86400 IN NS sava.utic.net.ba.
dig birac.ba @195.130.35.146 (linhost04)
;; QUESTION SECTION:
;birac.ba. IN A
;; ANSWER SECTION:
birac.ba. 86400 IN A 81.93.78.35
Using dig trace I can see the same behavior, sava does a horizontal referral, and if you are lucky, the next nameserver it picks is linhost4 on .146 that does answer the query
birac.ba. 86400 IN NS linhost04.utic.net.ba.
birac.ba. 86400 IN NS sava.utic.net.ba.
;; Received 121 bytes from 195.130.35.5#53(ns.ba) in 112 ms
birac.ba. 86400 IN NS linhost04.utic.net.ba.
birac.ba. 86400 IN NS sava.utic.net.ba.
;; BAD (HORIZONTAL) REFERRAL
;; Received 105 bytes from 195.130.35.3#53(sava.utic.net.ba) in 124 ms
birac.ba. 86400 IN NS sava.utic.net.ba.
birac.ba. 86400 IN NS linhost04.utic.net.ba.
;; BAD (HORIZONTAL) REFERRAL
;; Received 105 bytes from 195.130.35.3#53(sava.utic.net.ba) in 124 ms
birac.ba. 86400 IN NS linhost04.utic.net.ba.
birac.ba. 86400 IN NS sava.utic.net.ba.
;; BAD (HORIZONTAL) REFERRAL
;; Received 105 bytes from 195.130.35.3#53(sava.utic.net.ba) in 120 ms
birac.ba. 86400 IN NS sava.utic.net.ba.
birac.ba. 86400 IN NS linhost04.utic.net.ba.
;; BAD (HORIZONTAL) REFERRAL
;; Received 105 bytes from 195.130.35.3#53(sava.utic.net.ba) in 120 ms
birac.ba. 86400 IN NS linhost04.utic.net.ba.
birac.ba. 86400 IN NS sava.utic.net.ba.
;; BAD (HORIZONTAL) REFERRAL
;; Received 105 bytes from 195.130.35.3#53(sava.utic.net.ba) in 116 ms
birac.ba. 86400 IN A 81.93.78.35
birac.ba. 86400 IN NS ns1.birac.ba.
birac.ba. 86400 IN NS ns2.birac.ba.
;; Received 149 bytes from 195.130.35.146#53(linhost04.utic.net.ba) in 112 ms
If you do query linhost04 for the nameservers of birac.ba, it responds with ns1 and ns2 on birac.ba, both with the IP 195.130.35.146, which notably excludes Sava. But that doesn’t matter, the ones set at the registrar are the ones returned by the TLD nameservers and used by DNS resolvers, which are linhost04 and sava.
I’m guessing the difference here and why 1.1.1.1 doesn’t work is that it doesn’t follow horizontal referrals, or that it has a shorter loop limit then other resolvers. That, and it seems the owner of the website did intend to not have sava be a nameserver, but only changed the nameservers in their DNS, and not the ones at their registrar.
Thank you for your analisys Chaika.
I do not have control ofcourse.
I tried to contact and mention what you are implyng but at no result.
I will forward your report and try to convince them.
My question is can Cloudflare add the IP address 81.93.78.35 manually for birac.ba in their registry?
That would solve my problem would it not?
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.