Bintel website has been down since the early hours of last night

[dpastern]

I wonder if they're doing upgrades to their website, or didn't pay their hosting fees...

ping bintel.com.au (or www.bintel.com.au) comes up with unable to resolve host. Odd...

A whois shows the name servers:

Name Server: bt1.dnadigital.com.au
Name Server IP: 223.27.22.222
Name Server: bt2.dnadigital.com.au
Name Server IP: 223.27.22.222

doing a dig against 4.2.2.2 for NS records shows that this is indeed correct.

Doing a dig against both 4.2.2.2 and the bt1.dnadigital.com.au name servers for A records both give the same IP address:

223.27.22.222

which is can be pinged.

A telnet to the above IP address on port 80 just hangs (equivalent to the host not resolved message from a web browser).

nmap fails due to host down.

Anyone else noticed the site is down?

Dave

[julianh72]

It's working fine for me.
https://www.bintel.com.au/

[deanm]

Works for me, too.
Dean

[dpastern]

Excellent. Can you guys do a traceroute for me please?

Cheers,

Dave

edit: I'll turn wifi off on my iPhone and test it from there too.

What ISPS are you guys with? I'm with Optus (NBN fibre to home).

2nd edit: the site's IP address isn't blacklisted (that's good).

Looks like a routing issue can't route to the host name, and tracing the route to either the DNS server for the site, or the site's A record stops @ 175.45.117.198 (owned by vocus).

3rd edit: added 223.27.22.222 to my hosts file, pointing to bintel.com.au and www.bintel.com.au and site now browseable. My suspicion is that there's a routing issue on the Optus network to the DNS server for the bintel website.

[julianh72]

From my work desk in South Brisbane, so not sure of the ISP etc.

Traceroute:

Tracing route to bintel.com.au [223.27.22.222]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 10.145.135.1
2 1 ms 1 ms 1 ms 10.145.128.34
3 3 ms 2 ms 1 ms 61-68-35-77.static.tpgi.com.au [61.68.35.77]
4 2 ms 2 ms 2 ms au-ql-1688-ipg-01-eth-trunk2.2003.tpgi.com.au [203.221.87.17]
5 2 ms 2 ms 2 ms bri-sot-wic-wgw1-be-20.tpgi.com.au [203.219.166.72]
6 1 ms 1 ms 1 ms eth2-2.rq-127creek-cer-01.tpg-telecom.net [203.161.128.81]
7 26 ms 25 ms 25 ms ve100.rq-127creek-mlx-02.tpg-telecom.net [121.101.138.4]
8 26 ms 25 ms 25 ms eth3-16.rn-639gardeners-mlx-04.tpg-telecom.net [121.101.138.230]
9 25 ms 25 ms 25 ms eth1-7.rv-180burnley-mlx-01.tpg-telecom.net [121.101.138.217]
10 25 ms 25 ms 25 ms eth2-4.rv-55crockford-mlx-01.tpg-telecom.net [121.101.138.10]
11 26 ms 35 ms 25 ms ve100.rv-55crockford-cer-01.tpg-telecom.net [121.101.138.207]
12 26 ms 26 ms 25 ms ip-230-144-161-203.static.pipenetworks.com [203.161.144.230]
13 * * * Request timed out.
14 28 ms 26 ms 26 ms vmx19077.hosting24.com.au [223.27.22.222]

Trace complete.



Ping:

Pinging bintel.com.au [223.27.22.222] with 32 bytes of data:
Reply from 223.27.22.222: bytes=32 time=26ms TTL=50
Reply from 223.27.22.222: bytes=32 time=27ms TTL=50
Reply from 223.27.22.222: bytes=32 time=27ms TTL=50
Reply from 223.27.22.222: bytes=32 time=27ms TTL=50

Ping statistics for 223.27.22.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 27ms, Average = 26ms

[dpastern]

Many thanks Julian!

I can't get to the site from my iPhone either (Optus network, 4G). So definitely a routing issue @ Optus end.

[dpastern]

yeah, definitely Optus' name server. Querying it for bintel's A record comes up with no results. Probably a routing issue between the Optus DNS server and Bintel's DNS server.

Thanks guys!

[dpastern]

Meant to get a reply from Optus tier 3 techs within 24 hours of logging fault...hasn't happened.

Tier 1 tech earned my ire yesterday - after explaining the issue to him, and advising him that the issue was apparent on BOTH my iPhone using 4G and my home connection (using NBN fibre), what does he do? Not only does he remotely reboot my router, but he resets it back to factory defaults, killing my local wifi hotspot. Since I wasn't sure if he was pushing firmware updates to said router (been Six weeks since I last checked, so unlikely), I gave it 5 minutes as I didn't want to power cycle the router in the middle of a firmware update and bork it! In the end, connected to the default wifi on my MBP and didn't need to power cycle it, just go back in and update the password and then SSID name.

To say that I was ropable was an understatement!

Gave it a few hours to cool down, rang them, got another useless twit who didn't really seem to care that the prior tech had been useless and done the wrong thing. Supposed to get a call from the tech's manager, but that prolly won't happen.

Lesson earned in story - most ISP techs are useless and shouldn't be on a helpdesk imho. Optus' tech support is particularly bad.