- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
A Record Answer 127.0.0.1 of Authorotative record from Internet
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2023 07:19 AM
I have External and internal Views on Infoblox Grid , I have multiple zones on Internal & external Views with no issue, and running form a long time.
Today I created a zone on external view with some records.
When I do DIg & Nslookup for that record I am getting 127.0.0.1 answer, I tried nslookup and dig both.
I tried to trace using Dig and the query is traced to the Authoritative DNS server where I created Zone but the answer is 127.0.0.1.
Below is the out put from Intenet.
C:\Users\shaukat>dig www.x.x.x.x
; <<>> DiG 9.16.21 <<>> www.x.x.x.x
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59034
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.x.x.x.x. IN A
;; ANSWER SECTION:
www.x.x.x.x. 1 IN A 127.0.0.1
;; Query time: 53 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Sep 26 15:38:56 Arab Standard Time 2023
;; MSG SIZE rcvd: 60
I tried from the coroparate network which is pointing DNS query towards intenral and than external DNS and the repsonse is OK .It is giving proper response iI test using nslookup over there.
Does anyone face such issue? or any hint why it is happening so.
Thanks
Shaukat
Re: A Record Answer 127.0.0.1 of Authorotative record from Internet
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2023 07:20 AM
Hi,
THis issue i never faced earlier may be due to my configuration or any bug
Re: A Record Answer 127.0.0.1 of Authorotative record from Internet
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2023 12:23 AM
Resolved.