#dnscache

[softfindnet]

Steps to Clear DNS Cache on Chrome

💻🌐 Having trouble accessing websites on Chrome? 🤔💡Try clearing your DNS cache! 🔍💥 Follow these easy steps to get back online in no time! 🌟

[techdirectarchive]

(via Fix npm install hangs on "sill idealTree buildDeps")

[virtualizationhowto]

Best DNS Server you can Self-Host in 2023

Best DNS Server you can Self-Host #homelab #homeserver #selfhosted #dnsserver #bestdnsserver #topdnsprovider #DNScaching #nameresolution #itsalwaysDNS #virtualizationhowto #vexpert #technitium #pihole #adguard #powerdns #bind9 #dnsblackhole

Choosing a DNS Server for your home network or home lab environment is crucial to performance and security. There are many public DNS servers that can be used for DNS queries. However, in this post, we will look at the best DNS server you can self-host, with five options for the best features, security, and performance. Table of contentsSelecting the Best DNS Servers1. Technitium:…

[hackgit]

​Perfusion On Windows 7, Windows Server 2008R2, Windows 8, and Windows Server 2012, the...

​Perfusion On Windows 7, Windows Server 2008R2, Windows 8, and Windows Server 2012, the registry key of the RpcEptMapper and DnsCache (7/2008R2 only) services is configured with weak permissions. Any local user can create a Performance subkey and then leverage the Windows Performance Counters to load an arbitrary DLL in the context of the WMI service as NT AUTHORITY\SYSTEM (hence the tool's name). This tool is intended to help security consultants during penetration tests. This software is provided as is, and I will probably not provide any support. Though, I tested it thoroughly on three different virtual machines so there should not be any significant issue. https://github.com/itm4n/Perfusion For more information: https://itm4n.github.io/windows-registry-rpceptmapper-eop/

-

[wewpyousblog]

How to Fix DNS_PROBE_FINISHED_NXDOMAIN Error?

What Is DNS_PROBE_FINISHED_NXDOMAIN? 

Having a DNS_PROBE_FINISHED_NXDOMAIN Error message is a typical issue and more often than not this is a DNS-related issue. 

Space Name System is a kind of framework that permits you to visit sites by entering their location in an internet browser rather than an IP address. At the point when somebody is attempting to get to a site, the DNS sends a solicitation to an online data set and looks for the IP address associated with that URL. 

There are a few different ways to fix this issue, so we will address probably the most well-known reasons for this blunder message. 

1. Flush DNS Cache 

DNS store keeps the IP address of your recently visited locales. Clearing the store can assist with tackling DNS_PROBE_FINISHED_NXDOMAIN mistake since obsolete IP locations may be the reason for the issue. 

To flush the DNS store on Windows, you'll need to do the accompanying: 

1. Snap the Start button, look for the Command Prompt, and afterward right-snap to choose the Run as head alternative. 

2. When another window shows up, type in: 

ipconfig/flushdns 

3. At the point when you're set, click Enter. 

NOTE: If you're utilizing an alternate working framework, see our aide on How to Flush DNS on Linux and macOS. 

2. Delivery and Renew IP Address 

In the event that the past arrangement didn't get the job done, this is a more top to bottom method of clearing the DNS reserve which is like the past advance. 

Windows 

Open the Command Prompt regulatory rights very much like previously and enter the accompanying orders individually: 

You can deliver your present IP address by entering: 

ipconfig/discharge 

Assuming you need to show the full IP arrangement for the entirety of your connectors, utilize the accompanying: 

ipconfig/all 

To reset the DNS store, we'll use: 

ipconfig/flushdns 

This will reestablish arrangement settings for all connectors: 

ipconfig/reestablish 

Enter the accompanying orders to reset the IP settings of your recently put away IP and restore the Winsock Catalog. 

netsh int ip set dns 

netsh winsock reset 

Whenever that is done, restart your PC. 

Individuals utilize this cycle to restore their IP address and reset the Winsock on their frameworks. Resetting Winsock is valuable since it's liable for controlling solicitations from Internet applications and you might need to do as such on occasion. 

macOS 

Here's the means by which to deliver and restore an IP address on macOS: 

Go to System Preferences and snap Network 

Select your web association and tap Advanced 

Explore to the TCP/IP tab and snap Renew DHCP Lease 

Press OK and afterward restart your PC 

3. Change DNS Servers 

On the off chance that clearing the store doesn't work, you can change your DNS workers. As a matter of course, your PC is utilizing DNS given by your web access supplier. In case you're having issues, you can change that to Google DNS or OpenDNS. 

Windows 

Here's the way to change your DNS worker on Windows: 

Open the Control Panel menu and quest for Network and Sharing Center. 

On the left half of the window, click the Change connector settings alternative. 

Right-click on the association that you presently utilize and pick Properties. 

Discover the Internet Protocol Version 4 (TCP/IPv4) choice in the rundown and snap the Properties button once more. 

Under the General tab, you'll see two spaces at the lower part of the window — Preferred and Alternate DNS worker. Select the Use the accompanying DNS worker tends to choice and type in Google Public DNS IP addresses individually: 

8.8.8.8 

8.8.4.4 

Assuming you need to utilize OpenDNS, incorporate the accompanying: 

208.67.220.222 

208.67.222.220 

Whenever you're done, essentially click OK to save your changes. 

macOS 

Here's the means by which to change your DNS worker on macOS: 

Snap on the Apple symbol in the top-most left corner and explore to System Preferences. 

Select Network and pick the web association that you're right now utilizing. Hit the Advanced catch. 

Then, at that point, go to the DNS tab. Press the + catch and type in the new DNS worker – either Google Public DNS or OpenDNS, which are recorded previously. 

4. Restarting DNS Client Service 

One more technique incorporates restarting the DNS Client administration. There are three different ways how you can do this on Windows. 

Windows Command Prompt 

To reset the DNS administration from the order line, follow the means beneath: 

Open the Command Prompt 

To stop the DNS worker, input the accompanying order: 

net stop dnscache 

Once done, sit tight for the accompanying yield to be shown:

The DNS Client administration was halted effectively. 

Start the DNS administration again by composing: 

net beginning dnscache 

Hang tight for the yield: 

The DNS Client administration was begun effectively. 

Windows Services Manager 

Here's the way to restart DNS Client administration utilizing Windows Services: 

Access Services by composing it into the pursuit bar 

Look down and discover the DNS Client choice 

Snap the Restart Service button 

Windows System Configuration 

You can restart DNS Client administration utilizing the Windows System Configuration director. 

Press the Win + R keys on your console and enter msconfig in the hunt bar 

Select the Services tab, look down, and discover the DNS Client alternative 

Uncheck the container to incapacitate it 

Snap OK and afterward Restart 

Presently, proceed with stages one and two, however this time, review the crate to empower DNS Client 

Restart your PC once more 

5. Check Local Hosts File 

A hosts document is a neighborhood record on your PC that maps area names to IP addresses. Your PC will consistently allude to the hosts record first assuming you need to visit a site. Just in case there is no data, that it will look through the DNS framework to stack the site. 

So you should check if the site you're intending to visit is recorded there. It very well might be liable for setting off the DNS_PROBE_FINISHED_NXDOMAIN blunder. 

Windows 

To check the hosts record on Windows: 

Type Notepad in the pursuit bar and select Run as overseer 

Explore to File - > Open 

Change the record channel from Text Documents (*.txt) to All Files 

Duplicate the accompanying in the Address Bar: 

%SystemRoot%:\Windows\System32\Drivers\etc 

Double tap on the hosts document to get to it 

Opening the hosts document on Windows. 

In the event that the space name and IP address of the dangerous site are recorded, eliminate them, and afterward save your changes. 

Tweaking Windows has record. 

macOS 

Here's the way to check the hosts record on macOS. 

Open up your Terminal utilizing Launchpad 

Enter the accompanying order to run Nano Editor as an overseer: 

sudo nano/private/and so forth/has 

Info your secret key, and you'll be coordinated to the hosts record 

Eliminate the out of reach site's data, and afterward save your progressions by squeezing Control + O 

Tweaking macOS has record. 

6. Reset Chrome Flags 

Once in a while, one of the answers for fix the DNS_PROBE_FINISHED_NXDOMAIN mistake message is to attempt to reset Google Chrome settings and test includes that were inadvertently adjusted. To do this, type in the accompanying in your location bar: 

chrome://banners 

You'll gain admittance to all test Chrome highlights accessible. Snap Reset all catch on the upper right corner. Then, at that point close and resume your program. 

Significant: Google Chrome permits its clients to evaluate exploratory highlights. Since these are as yet a work in progress, not every one of them run as expected on certain gadgets. It may even wreck your association, so be cautious when utilizing them. 

Resetting Google Chrome trial highlights. 

7. Debilitate VPN or Antivirus 

Utilizing a VPN or antivirus programming offers staggering security answers for individuals who invest a great deal of energy on the web. Shockingly, these highlights can here and there keep clients from getting to certain sites. 

In case that is the situation, you might need to take a stab at winding down any dynamic VPN or antivirus to check whether that addresses the blunder. 

Impairing your antivirus is simple – you generally just need to open its control board and discover the alternative to briefly turn it off 

Then again, to cripple a VPN on Windows, kindly follow these means: 

Open the Control Panel and afterward go to Network and Internet - > Network Connections. 

Feature the VPN that you need to wind down and click Properties. 

Under the Networking tab, press Uninstall. Restart your PC to finish the interaction. 

8. Reaching Your Internet Provider 

On the off chance that the strategies above still don't tackle the DNS_PROBE_FINISHED_NXDOMAIN mistake, take a stab at restarting your web switch. Here's the manner by which to appropriately do as such: 

Turn off both your modem and switch, then, at that point hang tight for 30 seconds 

Fitting the modem back and sit tight for no less than two minutes 

Do likewise with your switch 

Check if the blunder is addressed 

In the case of all the other things falls flat, contact your internet service. Inquire as to whether there are any issues on their side or on the other hand on the off chance that they can work out an answer for you.

[noticias-enable]

21 de Abril, 2021

Internacional    

Corrigen parcialmente vulnerabilidad

Microsoft ha emitido silenciosamente una solución parcial para una vulnerabilidad de escalamiento de privilegios locales (LPE) que afecta a todos los dispositivos Windows 7 y Server 2008 R2. Esta vulnerabilidad de LPE (aún no rastreada oficialmente mediante un ID de CVE) se debe a la configuración incorrecta de dos claves de registro de servicios y permite a los atacantes locales escalar los privilegios en cualquier sistema completamente parcheado. Aprovechando este problema, los atacantes pueden ejecutar código arbitrario en el contexto del servicio Instrumental de administración de Windows (WMI) que se ejecuta con permisos del SISTEMA LOCAL.

 E.@. En resumen, un usuario no administrador local en la computadora simplemente crea una subclave de rendimiento en una de las claves anteriores, la llena con algunos valores y activa la supervisión del rendimiento, lo que lleva a un proceso WmiPrvSE.exe del sistema local que carga la DLL del atacante y la ejecución de código de la misma. Si bien Microsoft ha abordado silenciosamente el problema de la clave de registro RpcEptMapper (como lo descubrió 0patch) en la versión de Actualizaciones de Windows (ESU) de abril de 2021 al cambiar los permisos para que ya no incluya 'Crear subclave' para los grupos Usuarios y usuarios autenticados, la compañía todavía no solucionó la vulnerabilidad para DnsCache. 

Este error aún afecta a los dispositivos Windows 7 y Server 2008 R2, incluso si están inscritos en el programa de Actualizaciones de seguridad extendidas (ESU) de Microsoft o no hasta que Microsoft publique actualizaciones de seguridad para que los clientes de ESU aborden el problema por completo. 0patch lanzó una solución temporal en forma de un microparche gratuito que mitiga completamente el problema saboteando "las operaciones de monitoreo de desempeño para los dos servicios afectados, Dnsclient y RpcEptMapper".

 Fuente

[techdirectarchive]

(via How to fix npm install hangs on 'sill idealTree buildDeps')

[teknoloss]

Windows 7'de Yeni Bir Güvenlik Açığı Keşfedildi

Windows 7’de Yeni Bir Güvenlik Açığı Keşfedildi

Fransız güvenlik araştırmacısı Clément Labro, bir Windows güvenlik aracına yönelik güncelleme üzerinde çalışırken Windows 7 ve Windows Server 2008 R2 işletim sistemlerini etkileyen bir sıfırıncı gün güvenlik açığı tespit etti. Kelam konusu güvenlik açığı, RPC Endpoint Mapper ve DNSCache hizmetlerinin yanlış yapılandırılmış iki kayıt defteri anahtarında bulundu.

Labro’ya nazaran bir saldırgan,…

[gadgets360technews]

Security researcher accidentally discovers Windows 7 and Windows Server 2008 zero-day | ZDNet

Security researcher accidentally discovers Windows 7 and Windows Server 2008 zero-day | ZDNet

[ad_1]

Image: Microsoft

A French security researcher has accidentally discovered a zero-day vulnerability that impacts the Windows 7 and Windows Server 2008 R2 operating systems while working on an update to a Windows security tool.

The vulnerability resides in two misconfigured registry keys for the RPC Endpoint Mapper and DNSCache services…

[megasoyyer]

DNS service greyed out

also command “ipconfig /registerdns returns error “RPC server is unavailable”

I found the I was able to use regedit to disable dnscache.

I will say that it is ridiculous to lose the ability to change this from the services control panel. I also tried disabling it using msconfig and even unchecking the box didn't disable it.

Here are the directions the finally worked.

win+x run regedit

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Dnscache and locate Start registry key

Change Startup type :

Automatic -2 Manual -3 Disabled -4 Automatic (Delayed Start) -2

https://superuser.com/questions/1271946/dns-client-restart-greyed-out

[ryadel]

Windows Services complete list with ShortName and DisplayName

Here's a comprehensive list of most - if not all - Windows Service available nowadays on the major Windows operating systems - Windows 10, Windows Server 2016 and so on. The list shows the Display Name and the system's ShortName, which is the unique name used by the OS to locate and idenfity the service. The list should contain almost any known built-in service from both Windows and Windows Server: however, if you happen to find a missing one, feel free to write it in the comments section of this post, so that we'll be able to fill the gap! Display Name ShortName ActiveX Installer (AxInstSV) AxInstSV Adaptive Brightness SensrSvc Application Experience AeLookupSvc Application Host Helper Service AppHostSvc Application Identity AppIDSvc Application Information Appinfo Application Layer Gateway Service ALG Application Management AppMgmt ASP.NET State Service aspnet_state Background Intelligent Transfer Service BITS Base Filtering Engine BFE BitLocker Drive Encryption Service BDESVC Block Level Backup Engine Service wbengine Bluetooth Support Service bthserv BranchCache PeerDistSvc Certificate Propagation CertPropSvc Client for NFS NfsClnt CNG Key Isolation KeyIso COM+ Event System EventSystem COM+ System Application COMSysApp Computer Browser Browser Credential Manager VaultSvc Cryptographic Services CryptSvc DCOM Server Process Launcher DcomLaunch Desktop Window Manager Session Manager UxSms DHCP Client Dhcp Diagnostic Policy Service DPS Diagnostic Service Host WdiServiceHost Diagnostic System Host WdiSystemHost Disk Defragmenter defragsvc Distributed Link Tracking Client TrkWks Distributed Transaction Coordinator MSDTC DNS Client Dnscache Encrypting File System (EFS) EFS Extensible Authentication Protocol EapHost Fax Fax Function Discovery Provider Host fdPHost Function Discovery Resource Publication FDResPub Group Policy Client gpsvc Health Key and Certificate Management hkmsvc HomeGroup Listener HomeGroupListener HomeGroup Provider HomeGroupProvider Human Interface Device Access hidserv IIS Admin Service IISADMIN IKE and AuthIP IPsec Keying Modules IKEEXT Indexing Service CISVC Interactive Services Detection UI0Detect Internet Connection Sharing (ICS) SharedAccess IP Helper iphlpsvc IPsec Policy Agent PolicyAgent KtmRm for Distributed Transaction Coordinator KtmRm Link-Layer Topology Discovery Mapper lltdsvc LPD Service LPDSVC Media Center Extender Service Mcx2Svc Message Queuing MSMQ Message Queuing Triggers MSMQTriggers Microsoft .NET Framework NGEN v2.0.50727 clr_optimization_v2.0.50727 Microsoft FTP Service ftpsvc Microsoft iSCSI Initiator Service MSiSCSI Microsoft Software Shadow Copy Provider swprv Multimedia Class Scheduler MMCSS Net.Msmq Listener Adapter NetMsmqActivator Net.Pipe Listener Adapter NetPipeActivator Net.Tcp Listener Adapter NetTcpActivator Net.Tcp Port Sharing Service NetTcpPortSharing Netlogon Netlogon Network Access Protection Agent napagent Network Connections Netman Network List Service netprofm Network Location Awareness NlaSvc Network Store Interface Service nsi Offline Files CscService Parental Controls WPCSvc Peer Name Resolution Protocol PNRPsvc Peer Networking Grouping p2psvc Peer Networking Identity Manager p2pimsvc Performance Logs & Alerts pla Plug and Play PlugPlay PnP-X IP Bus Enumerator IPBusEnum PNRP Machine Name Publication Service PNRPAutoReg Portable Device Enumerator Service WPDBusEnum Power Power Print Spooler Spooler Problem Reports and Solutions Control Panel Support wercplsupport Program Compatibility Assistant Service PcaSvc Protected Storage ProtectedStorage Quality Windows Audio Video Experience QWAVE Remote Access Auto Connection Manager RasAuto Remote Access Connection Manager RasMan Remote Desktop Configuration SessionEnv Remote Desktop Services TermService Remote Desktop Services UserMode Port Redirector UmRdpService Remote Procedure Call (RPC) RpcSs Remote Procedure Call (RPC) Locator RpcLocator Remote Registry RemoteRegistry RIP Listener iprip Routing and Remote Access RemoteAccess RPC Endpoint Mapper RpcEptMapper SeaPort SeaPort Secondary Logon seclogon Secure Socket Tunneling Protocol Service SstpSvc Security Accounts Manager SamSs Security Center wscsvc Server LanmanServer Shell Hardware Detection ShellHWDetection Simple TCP/IP Services simptcp Smart Card SCardSvr Smart Card Removal Policy SCPolicySvc SNMP Service SNMP SNMP Trap SNMPTRAP Software Protection sppsvc SPP Notification Service sppuinotify SSDP Discovery SSDPSRV Storage Service StorSvc Superfetch SysMain System Event Notification Service SENS Tablet PC Input Service TabletInputService Task Scheduler Schedule TCP/IP NetBIOS Helper lmhosts Telephony TapiSrv Telnet TlntSvr Themes Themes Thread Ordering Server THREADORDER TPM Base Services TBS UPnP Device Host upnphost User Profile Service ProfSvc Virtual Disk vds Volume Shadow Copy VSS Web Management Service WMSVC WebClient WebClient Windows Audio AudioSrv Windows Audio Endpoint Builder AudioEndpointBuilder Windows Backup SDRSVC Windows Biometric Service WbioSrvc Windows CardSpace idsvc Windows Color System WcsPlugInService Windows Connect Now – Config Registrar wcncsvc Windows Defender WinDefend Windows Driver Foundation – User-mode Driver Framework wudfsvc Windows Error Reporting Service WerSvc Windows Event Collector Wecsvc Windows Event Log EventLog Windows Firewall MpsSvc Windows Font Cache Service FontCache Windows Image Acquisition (WIA) StiSvc Windows Installer msiserver Windows Live Family Safety fsssvc Windows Management Instrumentation Winmgmt Windows Media Center Receiver Service ehRecvr Windows Media Center Scheduler Service ehSched Windows Media Player Network Sharing Service WMPNetworkSvc Windows Modules Installer TrustedInstaller Windows Presentation Foundation Font Cache 3.0.0.0 FontCache3.0.0.0 Windows Process Activation Service WAS Windows Remote Management (WS-Management) WinRM Windows Search WSearch Windows Time W32Time Windows Update wuauserv WinHTTP Web Proxy Auto-Discovery Service WinHttpAutoProxySvc Wired AutoConfig dot3svc WLAN AutoConfig Wlansvc WMI Performance Adapter wmiApSrv Workstation LanmanWorkstation World Wide Web Publishing Service W3SVC WWAN AutoConfig WwanSvc   Read the full article

[spawn1t]

Cloud Zimbra Proxy

Well everything is pretty straight-forward here except one small thing that took me quite a while to troubleshoot. Please note, I've discussed the issue with two Zimbra Support Agents and they were not able to provide me with a clean solution (don't know if it's an incompetence to blame or poor zimbra architecture) so this is more of a workaround here. Fits the needs.

So I have Zimbra NE server on premises and since I'm not a big fan of exposing our public IP, I've decided to serve all external email needs with Zimbra Proxy + MTA hosted on AWS VM (I'm using CentOS 7). Please note, I already have one internal proxy configured on zimbra server, so proxying is enabled and I will not cover it here.

First, I'll install zimbra proxy on my AWS VM. It's quite simple, you can follow official documentation here, just make sure you download the same version that is installed on your main server.

./install Select the packages to install Install zimbra-ldap [Y] n Install zimbra-logger [Y] n Install zimbra-mta [Y] y Install zimbra-dnscache [N] n Install zimbra-snmp [Y] n Install zimbra-store [Y] n Install zimbra-apache [Y] n Install zimbra-spell [Y] n Install zimbra-memcached [Y] n Install zimbra-proxy [Y] y Install zimbra-archiving [N] n Checking required space for zimbra-core Installing: zimbra-core zimbra-mta zimbra-memcached zimbra-proxy zimbra-mta-patch zimbra-proxy-patch zimbra-license-tools

zimbra-memcached will be installed as prerequest for zimbra proxy Some additional configuration is required during the installation:

*Common configuration 1) Hostname: zimbraproxy.yallalinux.com ** 2) Ldap master host: UNSET -- zimbraserver.yallalinux.com 3) Ldap port: 389 ** 4) Ldap Admin password: UNSET -- ldap_root_password ** 5) LDAP Base DN: cn=zimbra 6) Store ephemeral attributes outside Ldap: no 7) Secure interprocess communications: yes 8) TimeZone: UTC 9) IP Mode: ipv4 10) Default SSL digest: sha256

To get ldap passwords from zimbra server:

[zimbra@zimbraserver ~]$ zmlocalconfig -s | grep password ldap_root_password = aNppQ3lLQdVZ

and use it on zimbra proxy:

******* +Bind password for nginx ldap user: Not Verified ldap_nginx_password = aNppQ3lLQdVZ

At this point, if ports are open between zimbra proxy and zimbra server and zimbra server DNS record is resolvable from zimbra proxy, services operating via 443 (webmail, activesync, zimbra outlook connector, etc) will work as expected.

But I needed my imap/smtp in place and this is were problems have started: (following is nginx log from proxy VM with debug* enabled)

2019/08/01 12:49:26 [debug] 15764#0: *9 zm_ngx_lookup_module: zm lookup http header: "Date: Thu, 01 Aug 2019 12:49:26 GMT" 2019/08/01 12:49:26 [debug] 15764#0: *9 zm_ngx_lookup_module: zm lookup http header: "Auth-Status: OK" 2019/08/01 12:49:26 [debug] 15764#0: *9 zm_ngx_lookup_module: zm lookup http header: "Auth-Server: 192.168.152.4" 2019/08/01 12:49:26 [debug] 15764#0: *9 zm_ngx_lookup_module: zm lookup http header: "Auth-Port: 7993" 2019/08/01 12:49:26 [debug] 15764#0: *9 zm_ngx_lookup_module: zm lookup http header: "Auth-Cache-Alias: FALSE" 2019/08/01 12:49:26 [debug] 15764#0: *9 zm_ngx_lookup_module: zm lookup http header: "Auth-User: test@yallalinux.com" 2019/08/01 12:49:26 [debug] 15764#0: *9 zm_ngx_lookup_module: zm lookup http header: "Vary: Accept-Encoding, User-Agent" 2019/08/01 12:49:26 [debug] 15764#0: *9 zm_ngx_lookup_module: zm lookup http header: "Content-Length: 0" 2019/08/01 12:49:26 [debug] 15764#0: *9 close connection 00007F3694CAC7A8 to nginx lookup handler XX.XXX.XX.XXX:7072 2019/08/01 12:49:26 [debug] 15764#0: *9 SSL_shutdown: 1 2019/08/01 12:49:26 [debug] 15764#0: *9 event timer del: 18: 1564663780977 2019/08/01 12:49:26 [debug] 15764#0: *9 event timer del: 18: 1564663780977 2019/08/01 12:49:26 [debug] 15764#0: *9 reusable connection: 0 2019/08/01 12:49:26 [debug] 15764#0: *9 zm lookup: done processing lookup headers 2019/08/01 12:49:26 [debug] 15764#0: *9 zm lookup: lookup handler XX.XXX.XX.XXX:7072 sent route 192.168.1.200:7993 2019/08/01 12:49:26 [debug] 15764#0: *9 posix_memalign: 00000000020EF7D0:256 @16 2019/08/01 12:49:26 [debug] 15764#0: *9 posting memcache request to cache server #0 2019/08/01 12:49:26 [debug] 15764#0: *9 posix_memalign: 00000000020F1E70:1024 @16 2019/08/01 12:49:26 [debug] 15764#0: *9 generate pdu add route:proto=imapssl;user=test@yallalinux.com 0 3600 18 192.168.1.200:7993

XX.XXX.XX.XXX is a public IP of zimbraserver host however zimbra server doesn't send mailbox server fqdn but resolves it locally instead and passes local IP to zimbra proxy, that is used later for account mail routing.

This is something I wasn't able to configure properly so had to bring some outbound DNATing as a workaround.

iptables -t nat -A OUTPUT -d 192.168.1.200 -j DNAT --to-destination XX.XXX.XX.XXX

At this point I was able to fully limit external access to zimbraserver and use AWS VM as an entry point from internet.

You will beed to configure some access rules from proxy to the server, please refer to official documentation https://wiki.zimbra.com/wiki/Ports

tcp/11211 tcp/8443 tcp/7993 tcp/389 tcp/7072 tcp/7073 tcp/7025 tcp/22 udp/514 tcp/53 udp/53

please note that Amazon EC2 throttles traffic on port 25 of all EC2 instances by default, but you can request for this throttle to be removed.

To enable debug, change nginx logging level on zimbraproxy

zmprov ms `zmhostname` zimbraReverseProxyLogLevel debug

[webdesignersolutions]

I am in the process of of migrating all of my Linodes to Digital Ocean and I was hoping someone could provide some guidance. Last night I migrated my first Linode to Digital Ocean with the domain with no problems whatsoever, it was a 10 minute process.

After that I created my second droplet and repeated the same steps as I did for the first one but I can’t manage to get the domain to successfully transfer to that droplet. I changed the name servers from linode to digital ocean and I linked the domain to the new dropplet. I also deleted that domain from my Linode account, however that Linode is somehow still serving that domain if I power that Linode back up.

When I look up the domain name on mxtoolbox.com it says it is linked to the digital ocean droplet ip address which leads me to believe that the propagation is complete, is that wrong?

The droplet I created is a Dokku image so to deploy I add “`git add remote dokku dokku@dokku.me:dokku.me“` but when I git push dokku master it still tries to connect to my linode ip address.

I erased that IP address from my ~/.ssh/known_hosts file as well as the domain name entry in that file and I also cleared the local DNScache from my mac.

What am I missing? Do I just need to wait for the propagation to finish?

Submitted May 15, 2019 at 08:13AM by the-impostor https://www.reddit.com/r/webhosting/comments/boz4z3/migrating_from_linode_to_digital_ocean/?utm_source=ifttt

from Blogger http://webdesignersolutions1.blogspot.com/2019/05/migrating-from-linode-to-digital-ocean.html via IFTTT

[hibritteknoloji]

Yeni bir gönderi var Burak ALTIPARMAK

New Post has been published on https://burakaltiparmak.com.tr/windows-dns-temizleme/

Windows DNS Temizleme

İnternette dolaşırken hiç DNS hatası aldınız mı? Sadece aynı ağa bağlı başka bir aygıt sorunsuz bir halde mi çalışıyor? Bunu düzeltmeniz için DNS önbelleğini temizleyerek problemi çözebilirsiniz.

DNS Önbelleğini Temizle

Komut istemini yönetici olarak çalıştırın. Bunun için başlat tıklayın ve aramaya ”Komut İstemi” yazın. Komut istemini sağ tıklayıp ”Yönetici olarak çalıştır” tıklayın.

Komut istemine aşağıdaki kodu yazın ve enter basın.

ipconfig /flushdns

Bu komut, Windows 10, 8, 7, Vista ve XP de dahil olmak suretiyle tüm Windows sürümlerinde çalışır.

Bu komutu çalıştırarak birçok problemi çözebilirsiniz. Sadece bazı uygulamalarda mesele yaşıyorsanız, uygulamanın DNS önbelleğinde problem oluşmuş olabilir. Mesela, Firefox‘un kendi dahili DNS önbelleği vardır, Firefox‘ta problem yaşıyorsanız onu kapatıp tekrardan açmak yada tarayıcı ayarlarını temizlemek isteyebilirsiniz.

DNS Hizmetini Tekrardan Başlat

Windows’un eski sürümlerinde, DNS önbelleğini işleyen DNS İstemcisi sistem hizmetini tekrardan başlatmayı da deneyebilirsiniz. Windows 10 ve 8‘de bu hizmetin durdurulmasını ve başlatılmasını önleyen bu mümkün değildir; yalnızca denerseniz bir hata mesajı görürsünüz. Sadece, bunu Windows 7, Vista ve XP’de yapabilirsiniz.

Windows’un daha eski bir sürümünü kullanıyorsanız, bunu aslına bakarsanız açık olan Yönetici Komut İstemi penceresinden yapabilirsiniz. Sırayla aşağıdaki komutları çalıştırın:

net stop dnscache net start dnscache

Problem yaşıyorsanız ve Windows 10‘da bu hizmeti tekrardan başlatmanız gerekiyorsa, bilgisayarınızı tekrardan başlatmanız kafi olacaktır. Bu cihazınızdaki DNS İstemcisi hizmetini ve öteki tüm yazılımları tekrardan başlatır.