Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

DNS resolution errors on UPC Horizon?

Options
  • 12-01-2014 9:46pm
    #1
    donal.hunt
    Registered Users Posts: 334 ✭✭


    checking in here in case others have experienced this...

    I've been encountering webpage load problems over the past few days. Narrowed it down to a DNS resolution issue. From what I've been seeing, the horizon box is timing out while trying to resolve addresses.

    Thing is, my horizon box is set to use 8.8.8.8 and 8.8.4.4 dns servers which are resolving the relevant web addresses just fine...


    === Errors observed with DNS responses from horizon box (192.168.0.1) ===

    $ dig @192.168.0.1 developers.google.com
    ;; Warning: ID mismatch: expected ID 52091, got 0
    ;; Warning: query response not set
    ;; Warning: ID mismatch: expected ID 52091, got 0
    ;; Warning: query response not set

    $ dig @192.168.0.1 mail.google.com
    ;; Warning: ID mismatch: expected ID 52091, got 0
    ;; Warning: query response not set
    ;; Warning: ID mismatch: expected ID 52091, got 0
    ;; Warning: query response not set


    $ dig @192.168.0.1 ib.adnxs.com
    ;; Warning: ID mismatch: expected ID 28675, got 0
    ;; Warning: query response not set
    ;; Warning: ID mismatch: expected ID 28675, got 0
    ;; Warning: query response not set
    ;; Warning: ID mismatch: expected ID 28675, got 0
    ;; Warning: query response not set

    ; <<>> DiG 9.8.1-P1 <<>> @192.168.0.1 ib.adnxs.com
    ; (1 server found)
    ;; global options: +cmd
    ;; connection timed out; no servers could be reached



    === Direct queries to these DNS servers while this issue is observed are returned perfectly fine ===


    $ dig @8.8.8.8 developers.google.com

    ; <<>> DiG 9.8.1-P1 <<>> @8.8.8.8 developers.google.com
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11110
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;developers.google.com. IN A

    ;; ANSWER SECTION:
    developers.google.com. 21600 IN CNAME www3.l.google.com.
    www3.l.google.com. 300 IN A 74.125.24.139
    www3.l.google.com. 300 IN A 74.125.24.101
    www3.l.google.com. 300 IN A 74.125.24.100
    www3.l.google.com. 300 IN A 74.125.24.113
    www3.l.google.com. 300 IN A 74.125.24.138
    www3.l.google.com. 300 IN A 74.125.24.102

    ;; Query time: 37 msec
    ;; SERVER: 8.8.8.8#53(8.8.8.8)
    ;; WHEN: Sat Jan 11 23:27:55 2014
    ;; MSG SIZE rcvd: 156

    =======================================================

    Have filed a support request with UPC but wanted to check and see if anyone has seen anything similar in recent days?
    Tagged:


Comments

  • Options
    #2
    donal.hunt
    Registered Users Posts: 334 ✭✭donal.hunt


    BTW - Anyone got the default UPC dns servers handy so I can rule out my custom dns servers?


  • Options
    #3
    donal.hunt
    Registered Users Posts: 334 ✭✭donal.hunt


    the default upc dns servers appear to be:

    89.101.160.4 ie-dub01a-dns01.upc.ie.
    89.101.160.5 ie-dub01a-dns02.upc.ie.


  • Options
    #4
    fermi-paradox
    Registered Users Posts: 36 ✭fermi-paradox


    Hi Donal,
    Sorry to interrupt your soliloquy here, but as you commented on my thread in Ask.UPC I'd be interested to know if you have any idea what is going on here.

    My horizon box is at 192.168.1.1 and 
    dig @192.168.1.1 mail.google.com

; <<>> DiG 9.8.3-P1 <<>> @192.168.1.1 mail.google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44929
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;mail.google.com.		IN	A

;; ANSWER SECTION:
mail.google.com.	77116	IN	CNAME	googlemail.l.google.com.
googlemail.l.google.com. 183	IN	A	74.125.24.83
googlemail.l.google.com. 183	IN	A	74.125.24.17
googlemail.l.google.com. 183	IN	A	74.125.24.18
googlemail.l.google.com. 183	IN	A	74.125.24.19

;; Query time: 64 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Sun Jan 19 18:53:23 2014
;; MSG SIZE  rcvd: 124

    to borrow your example, works fine.
    dig whoami.akamai.com +short
whoami.akamai.net.
89.101.160.9

    which says it resolved through 89.101.160.9 which seems to be
    ie-dub01a-dns02o.upc.ie,
    yet another server.

    But
    dig  @192.168.1.1  www.usccb.org

; <<>> DiG 9.8.3-P1 <<>> @192.168.1.1 www.usccb.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 12429
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;www.usccb.org.			IN	A

;; Query time: 910 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Sun Jan 19 19:17:54 2014
;; MSG SIZE  rcvd: 31

    while
    dig  @8.8.8.8  www.usccb.org

; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 www.usccb.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23051
;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.usccb.org.			IN	A

;; ANSWER SECTION:
www.usccb.org.		600	IN	CNAME	d38hr0jzr0onlo.cloudfront.net.
d38hr0jzr0onlo.cloudfront.net. 60 IN	A	216.137.57.220
d38hr0jzr0onlo.cloudfront.net. 60 IN	A	54.230.31.187
d38hr0jzr0onlo.cloudfront.net. 60 IN	A	216.137.57.131
d38hr0jzr0onlo.cloudfront.net. 60 IN	A	54.230.31.97
d38hr0jzr0onlo.cloudfront.net. 60 IN	A	54.230.31.135
d38hr0jzr0onlo.cloudfront.net. 60 IN	A	54.230.28.180
d38hr0jzr0onlo.cloudfront.net. 60 IN	A	216.137.57.162
d38hr0jzr0onlo.cloudfront.net. 60 IN	A	54.230.28.45

;; Query time: 205 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sun Jan 19 19:05:12 2014
;; MSG SIZE  rcvd: 202

    I'm certain {I think} that something is broken now and that it all worked before horizon started ignoring DNS server settings, but I am not sure what.

    Anyway, if you hear of a resolution to this from UPC please, if you would be kind enough, update the Ask.UPC thread and I will do the same.


  • Options
    #5
    donal.hunt
    Registered Users Posts: 334 ✭✭donal.hunt


    fermi-paradox: sorry! Only saw your update now...

    may or may not be related. the bug I seem to be triggering gives those mismatch warnings. Haven't seen many cases of getting no result (and no mismatch). Any time I have, a second attempt results in getting the right results.

    If unplugging the horizon box and replugging it results in the dns resolving then it's potentially related. Only thing you can do is file a support request with as much data as possible. The intermittent nature of it means it's probably not a high priority. :/

    I have an engineer booked for wednesday so will either be getting the problem fixed or switching to a different solution.

    p.s. that site results fine for me.


  • Options
    #6
    lpw
    Registered Users Posts: 27 ✭lpw


    Ha - yeah - been meaning to file a ticket myself - had problems since Paddy's day - which I think are primarily related to DNS. Primary symptoms;

    * random web browsing, sites will just not resolve
    * not local network (everything behaving as expected)
    * when a connection is established, performance is fast as expected.

    It is incredibly annoying as basically it sees to happen randomly every 5-10 minutes and lasts in the order of 5secs - 1 minute. Massive pain in the whole

    Update:

    Forgot to say was also rolling with 8.8.8.8/.4.4 - so am now trying to default back - but again a pain as i've had it set in a few places (wifi router, cable modem, individual devices)

    From memory - to get back to the defaults it's basically just to leave the DNS fields blank.


  • Advertisement
Advertisement