All.. You're welcome for the info.
Let's remember what NANOG is about "mailing list is established to provide a
forum for the exchange of technical information and the discussion of specific
implementation issues that require cooperation among network service providers."
I sent this out to educ
Shaun, Good catch!!!
I would be nice if this was lowered to 1 second.
#dig o-o.myaddr.l.google.com -t txt @8.8.4.4
;; ANSWER SECTION:
o-o.myaddr.l.google.com. 51 IN TXT "74.125.80.4"
o-o.myaddr.l.google.com. 51 IN TXT "edns0-client-subnet
14.161.5.0/24" <<< Not my ip
Excellent, thanks for sharing.
El 23/8/17 a las 4:09 p.m., Erik Sundberg escribió:
> I sent this out on the outage list, with a lots of good feedback sent to me.
> So I figured it would be useful to share the information on nanog as well.
>
>
> A couple months ago had to troubleshoot a google DN
So yesterday I started seeing some arp warnings in my server logs:
Aug 23 16:09:29 lisa /bsd: arp info overwritten for 96.251.22.154 by
f0:1c:2d:8d:0e:cf on em2
Aug 23 16:12:24 lisa /bsd: arp info overwritten for 96.251.22.154 by
f0:1c:2d:8d:0e:cf on em2
Aug 23 16:21:28 lisa /bsd: arp info overwri
If Google was being sensible the servers would just return the
information along with the answer. They all support EDNS.
e.g. dig +nsid @8.8.8.8
This is the type of thing the NSID (RFC 5001) was designed to do.
It just requires Google to configure the servers to return a id.
You would t
On Wed, Aug 23, 2017 at 8:30 PM, Joe Hamelin wrote:
> Gee Chris, that's kind of an asinine response. Erik took the time to let
> us know about what he had found out, with
>
sure, except I think the link has even been posted to nanog in the past.
My point was really: it's documented, so you don'
On Wed, Aug 23, 2017 at 4:37 PM, i mawsog via NANOG wrote:
>
> This is great. Thanks for sharing .
>
> Sent from Yahoo Mail on Android
>
> On Wed, Aug 23, 2017 at 1:11 PM, Erik Sundberg
> wrote: I sent this out on the outage list, with a lots of good feedback
> sent to me. So I figured it wo
This is great. Thanks for sharing .
Sent from Yahoo Mail on Android
On Wed, Aug 23, 2017 at 1:11 PM, Erik Sundberg wrote:
I sent this out on the outage list, with a lots of good feedback sent to me.
So I figured it would be useful to share the information on nanog as well.
A couple m
I sent this out on the outage list, with a lots of good feedback sent to me. So
I figured it would be useful to share the information on nanog as well.
A couple months ago had to troubleshoot a google DNS issue with Google’s NOC.
Below is some helpful information on how to determine which DNS C
In article
you write:
>Thank you for your assistance. I'm used to query AS entries for LACNIC
>region and their WHOIS spit out righ away all contacts. I didn't realise I
>had to make a secondary query for the Technical Contact ID to only then see
>the e-mail address.
If you do write to Japanese
* lis...@kurtkraut.net (Kurt Kraut) [Wed 23 Aug 2017, 17:16 CEST]:
No e-mail addresses of the abuse team or NOC or SOC.
| % whois 59.106.13.181 | grep support
| remarks:Email address for spam or abuse complaints :
supp...@sakura.ad.jp
That's not a special whois client but is in the te
Hello folks,
Thank you for your assistance. I'm used to query AS entries for LACNIC
region and their WHOIS spit out righ away all contacts. I didn't realise I
had to make a secondary query for the Technical Contact ID to only then see
the e-mail address.
Best regards,
Kurt Kraut
2017-08-23 12
Kurt
I see contact info for KW419JP maybe I don't understand what you are
looking for.
On Wed, Aug 23, 2017 at 10:16 AM, Kurt Kraut wrote:
> Hello Suresh,
>
>
> It doesn't seem to help a lot:
>
> ktk@ktk:~$ whois -h whois.nic.ad.jp 59.106.13.181
> [ JPNIC database provides information regarding
On Wed, 23 Aug 2017, Kurt Kraut wrote:
Network Information:
a. [Network Number] 59.106.12.0-59.106.27.255
b. [Network Name] SAKURA-NET
g. [Organization] SAKURA Internet Inc.
m. [Administrative Contact] KT749JP
n. [Technical Contact] KW419JP
N
Hello Suresh,
It doesn't seem to help a lot:
ktk@ktk:~$ whois -h whois.nic.ad.jp 59.106.13.181
[ JPNIC database provides information regarding IP address and ASN. Its use
]
[ is restricted to network administration purposes. For further
information, ]
[ use 'whois -h whois.nic.ad.jp help'. To
whois -h whois.nic.ad.jp IP /e
--srs
> On 23-Aug-2017, at 7:38 PM, Kurt Kraut wrote:
>
> Hello,
>
>
> I'm having a hard time to figure out the abuse e-mail address for IPs from
> Japan. Any query I perform at the WHOIS, for any IP, from any autonomoyus
> system I get the same e-mail addresses
Hello,
I'm having a hard time to figure out the abuse e-mail address for IPs from
Japan. Any query I perform at the WHOIS, for any IP, from any autonomoyus
system I get the same e-mail addresses:
ab...@apnic.net
hm-chan...@apnic.net
ip-ap...@nic.ad.jp
hostmas...@nic.ad.jp
These e-mail addresses
Call for Participation -- ICANN DNSSEC Workshop at ICANN60 in Abu Dhabi, UAE
The DNSSEC Deployment Initiative and the Internet Society Deploy360 Programme,
in cooperation with the ICANN Security and Stability Advisory Committee (SSAC),
are planning a DNSSEC Workshop during the ICANN60 meeting he
Hoping a Cisco WebEx Tech Support Expert can contact me offline ASAP on an
urgent matter.
Thank you. Before 10:45am ET today please.
Thank you.
--
*Ilissa Miller*
CEO, *iMiller Public Relations*
www.imillerpr.com
email: ili...@imillerpr.com
> Things that most people generally agree on include:
>
> - carefully splitting out service types. E.g. a fibre cable to a
> location is one ID; a wavelength on that service is another ID of
> another type; an IP transit service on that wave is a third ID, etc.
Definitely. We have one digit in o
20 matches
Mail list logo