Fwd: DHCP pool forward lookup issue on IETF net?
| Reported by: |
jim@… |
Owned by: |
rob@… |
|
Priority:
|
tbd
|
Milestone:
|
ietf-098
|
|
Component:
|
dns
|
Keywords:
|
|
|
Cc:
|
|
My Current Location:
|
|
|
My MAC Address:
|
|
My OS:
|
|
Begin forwarded message:
> From: Jim Reid <jim@rfc1035.com>
> Date: March 25, 2017 at 10:57:17 PM CDT
> To: Jim Martin <jim@daedelus.com>
> Subject: DHCP pool forward lookup issue on IETF net?
>
> Hi Jim. Could you please forward this error report to the right place or tell me how to reach it? Ta.
>
>
> gromit% dig -x 31.133.184.233
>
> ...
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 4096
> ; COOKIE: 7cfb839312ff752dc7bbd64858d73b274b2a7bac2d283693 (good)
> ;; QUESTION SECTION:
> ;233.184.133.31.in-addr.arpa. IN PTR
>
> ;; ANSWER SECTION:
> 233.184.133.31.in-addr.arpa. 3600 IN PTR dhcp-b8e9.meeting.ietf.org.
> ...
>
> gromit% dig dhcp-b8e9.meeting.ietf.org
>
> ...
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 345
Change history (4)
| Component: |
incoming →
dns
|
| Owner: |
changed from < default > to rob@…
|
| Status: |
new →
assigned
|
| Type: |
request →
defect
|
| Status: |
assigned →
accepted
|
| Resolution: |
→ fixed
|
| Status: |
accepted →
closed
|
| Milestone: |
ietf-98 →
ietf-098
|
I will be working on this ticket this morning and get a response out asap.